|
Kanban is a method for managing knowledge work with an emphasis on just-in-time delivery while not overloading the team members. In this approach, the process, from definition of a task to its delivery to the customer, is displayed for participants to see. Team members pull work from a queue. Kanban in the context of software development can mean a visual process-management system that tells what to produce, when to produce it, and how much to produce - inspired by the Toyota Production System〔 〕 and by Lean manufacturing.〔 〕 == Overview == David Anderson was among the first to formulate the Kanban Method for application to IT and software development in his 2010 book ''Kanban''.〔 〕 A notable earlier contribution came from Corey Ladas, whose 2009 book ''Scrumban''〔 〕 was the first to suggest that Kanban was a superior alternative to Scrum for software development. Corey's book saw Scrumban as the transition from the starting point of Scrum to the destination of Kanban. More recently, in 2013, Joseph Hurtado introduced (Open Kanban ), an open source, minimal, Agile and Lean method that is designed to be extended and customized. In addition, the (Kanban Ace ) was written as an extension of Open Kanban particularly suited to software development. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Kanban (development)」の詳細全文を読む スポンサード リンク
|